-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Containerfile #5141
Containerfile #5141
Conversation
python3-venv \ | ||
unzip \ | ||
vim \ | ||
libmpich-dev \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to do anything to get GPU-Aware MPI on Perlmutter to run?
Vanilla without containers, I have to set this to tell the Cray compiler wrappers to get it right:
# necessary to use CUDA-aware MPI and run a job
export CRAY_ACCEL_TARGET=nvidia80
Since we compile with GCC here, I am not sure how to do it.
@@ -0,0 +1,151 @@ | |||
# Base System and Essential Tools Installation | |||
FROM nvidia/cuda:12.6.0-devel-ubuntu22.04 AS base |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To test: we could use -devel
to build all dependencies but then copy their artifacts in the -runtime
image. To check if those are much smaller or not.
Co-authored-by: Axel Huebl <[email protected]>
Co-authored-by: Axel Huebl <[email protected]>
Co-authored-by: Axel Huebl <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a developer container for now.
Will expand in follow-up PRs to create also a user-image from it that can be used right away without compiling WarpX inside it first.
Containerfile to run WarpX at NERSC
To Do
shifter
instead of podman